The recent change that were made to the way Varnish handles cookies has caused it to reject logins if there is not a valid 'ljloggedin' cookie, whereas the client protocol only passes the 'ljsession' cookie to LiveJournal. We're in the process of changing this so that the login attempts sent with an 'ljsession' cookie will be considered valid ( Read more... )

Release 86 is out and those who use certain browser extensions to log into Livejournal are finding themselves unable to do so. Also, several users are finding that they are logged out randomly between redirect screens on the site. I'm guessing that these are related. A staff member commented in the release 86 post that something was changed in the ( Read more... )

I've just discovered that I can't get any challenges anymore in my LJ client. I get an error response saying that I did not specify a mode. But until ten minutes ago, everything was working fine...

( Telnet session in here )

I'm currently working on integrating Scrapbook in my LJ client. When downloading pictures, I got a 403 Forbidden error when downloading pictures that were under a friends-lock. That's (of course) exactly as it should be.
So my strategy is to get an LJ session cookie (through the sessiongenerate interface call) and send that along with my request ( Read more... )

Just writing my own LJ client in C# and was bumping into a strange problem with the challenge/response method of logging in ( Read more... )

I know perfectly well how to obtain the cookie associated with the SessionGenerate call - that's no problem. I'm completely confused as to what to do with that cookie to make my browsers stay logged in. I'm using Visual Basic 2008, and the browsers in question are not calls to the user's default browser, but internal WebBrowser forms. I don't know ( Read more... )

Long story short: I'm writing a client in Visual Basic 2008, and while I have no problem obtaining the cookie provided by SessionGenerate, I'm having a devil of a time figuring out how to set the cookie. As usual, Micro$oft's documentation is about as clear as mud on the matter, usually saying that it's the server responsibility. Some of this is ( Read more... )